FIM 2010 interface freezing with message "Enumerating Management Agents"
I have a server with Windows 2008 R2 Enterprise that I have installed FIM 2010 on. This server also has SQL Server 2008 64 bit SP1 and Visual Studio 2008 SP 1. After a few days of working on this new server, the FIM interface freezes up. The operating system was reinstalled along with all of the supporting software mentioned and after a couple of days, I am experiencing the same issue again. If I end the miisclient.exe process and restart it, the message of "Enumerating Management Agents" displays on the Management Agent tab and does nothing else for several minutes before finally loading management agents and run history. This problem seems to occur after a build on extension files in Visual Studio. If I reboot the server, the FIM interface loads fine and then will freeze again after a build of an extension. Has anyone run into this problem? Is .Net getting corrupted and causing FIM to hang? Thanks, BrandonBrandon McNabb
November 3rd, 2010 12:32pm

Brandon, Something you might check is your run history. If you have not cleared it in either a while or ever, it can very large and cause symptoms similar to what you are seeing. The total amount of runs is at the bottom righ in the Operations screen. If you suspect this is problem, after operations list does show up, you can go to 'Actions' from menu and choose 'Clear Runs'. This will allow you to remove runs up to a certain point in time, 2 weeks ago, for example. This can take quite a while(hours) to execute and often will leave the box in a state where it is unresponsive. The recommendation is to do this in chunks as opposed to deleting entire run history at once. This should reduce the size of the DB and make the system more responsive in general.
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2010 1:54pm

Glenn, The Synchronization Service database file is at 9.6 gb and resides on a drive of 400 gb of capacity. The server has 64 gb of RAM and 2 processors with 12 cores each. I don't believe this is the issue but I will clear some run history and let you know if this helps. The problem seems to manifest itself after I build an extension file in Visual Studio and then attempt to execute a run (usually an import and synchronization). Thanks, BrandonBrandon McNabb
November 3rd, 2010 3:28pm

Trimming the run history did not help. When I build an extension in Visual Studio and then attempt to engage the FIM client, it is frozen for 5 minutes or so. If I use task manager to stop the FIM client and then open it, the message "Enumerating Management Agents" is displayed and I still have to wait about 5 minutes before the interface is operational. Brandon McNabb
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 10:01am

Brandon, You have mentioned an approximate 5 minute interval several times; this is the length of time that the miiserver.exe process keeps extensions in memory for, even after being idle. I would be interested in seeing your Initialize function code for the extension in question, this symptom seems as though it could happen if when this function fires, it is getting caught in some kind of loop/no-end scenario. Ending the client simply restarts the UI, it won't take the extension out of memory. If you restart the miiserver.exe process instead, Iwould think this would make your sync engine responsive again until you run a sync on whatever MA you are using this extension for.
November 4th, 2010 10:48pm

I have a total of 15 management agents connecting to Active Directory, ADAM, Novell, SQL and a text file. Of the 15 ma's, 9 of them have extensions. Of the 9 extensions, only 1 has anything in the Initialize function. It is the ADAM extension and looks like this: void IMASynchronization.Initialize() { //log = new OH.Logging("ADAM"); seeif = new OH.Helper(); myEntry = new OH.AuditEntry(); } This is referencing a couple of custom classes. Brandon McNabb
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 12:45pm

What do the constructors for OH.Helper and OH.AuditEntry do?My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com
November 5th, 2010 1:09pm

The Helper constructor contains a series of methods that return flags to determine actions in my code. Example method from Helper: public bool ALPS(string empStatus) { if (empStatus.ToLower() == "a" || empStatus.ToLower() == "l" || empStatus.ToLower() == "p" || empStatus.ToLower() == "s") return true; else return false; } so, myEntry.ALPS("A") would return true and I know that a user is active in our Peoplesoft system. The AuditEntry constructor logs certain actions to a SQL db. Brandon McNabb
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 1:21pm

You might try ruling out that code by commenting it out, or turning off the extension. Is there anything in the event log? Do you have a FIM MA installed?CraigMartin Edgile, Inc. http://identitytrench.com
November 5th, 2010 1:37pm

I'll get that code and it's references commented out and give it a run. There are no errors reported in the event log or the sql logs when the interface hangs. FIM MA? I have several management agents that I am using.Brandon McNabb
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 1:53pm

I'd probably go get a dump of the miiserver process when this happens and take a look at what it's hung up on. Sounds like either a) there's a deadlock or b) some thread is spinning and consuming all the bandwidth/time.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com
November 5th, 2010 1:58pm

The reason I ask about the FIM MA is because sync engine will communicate with the FIM Service to update <ma-data> and <mv-data> objects. It could lead to delays in miisclient.exe, but I don't think I've seen it hang the client.CraigMartin Edgile, Inc. http://identitytrench.com
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 3:42pm

I changed the authentication mode on SQL server to Windows only from mixed and the FIM interface is not hanging. I am making changes to extensions and management agents attempting to duplicate the freezing issue but have not been able to yet. I will update if the freezing occurs again or if I don't see the issue again.Brandon McNabb
November 8th, 2010 9:50am

Changing the authentication mode did not resolve the issue. I added a direct mapping of an attribute for import on a sql management agent. As soon as I clicked ok, the interface froze. Now to get a dump of the miisserver process and report back.Brandon McNabb
Free Windows Admin Tool Kit Click here and download it now
November 9th, 2010 1:07pm

The issue turned out to be a connection in some Novell code not being closed properly. Waiting for that connection to close was causing the delay in FIM. Thanks for the assistance and time from everyone. Now I just need FIM to be certified for Oracle 11g.Brandon McNabb
November 10th, 2010 12:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics